Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1628

reference: 958-tree-1
name: 1628
tree-preservation-order: undefined
958-tpo-1
uprn
address-text
point: POINT (-1.036293 50.875517)
geometry: MULTIPOLYGON (((-1.036265 50.875514,-1.036266 50.875520,-1.036270 50.875525,-1.036277 50.875529,-1.036293 50.875532,-1.036302 50.875532,-1.036310 50.875529,-1.036316 50.875525,-1.036322 50.875515,-1.036321 50.875509,-1.036317 50.875504,-1.036303 50.875497,-1.036294 50.875496,-1.036285 50.875497,-1.036277 50.875500,-1.036271 50.875504,-1.036265 50.875514)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL